response
authorJoey Hess <joeyh@joeyh.name>
Wed, 29 Jan 2025 16:06:22 +0000 (12:06 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 29 Jan 2025 16:06:22 +0000 (12:06 -0400)
doc/forum/Reasonable_annex.bloomcapacity__63__/comment_1_0361164f67f44520f3af5ba88adc3868._comment [new file with mode: 0644]

diff --git a/doc/forum/Reasonable_annex.bloomcapacity__63__/comment_1_0361164f67f44520f3af5ba88adc3868._comment b/doc/forum/Reasonable_annex.bloomcapacity__63__/comment_1_0361164f67f44520f3af5ba88adc3868._comment
new file mode 100644 (file)
index 0000000..2a63d58
--- /dev/null
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2025-01-29T15:54:19Z"
+ content="""
+What will happen with too small a bloom filter is `git-annex unused` may
+think that some keys are used which are really not. And 
+`git-annex sync --content` may operate on some keys that are not in the
+work tree.
+
+The `git-annex info` command displays how much memory the configured bloom
+filters use, which is why it's reporting 32 membibytes. But the
+annex.bloomcapacity setting is the number of expected files in the work
+tree, by default 500000.
+
+It would probably make sense for you to set it to 2000000 or so unless
+your system has an unusually small amount of RAM.
+"""]]